Add queryfilter package and ExpectResourceDisplayNameExact query check
#573
+841
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue
Fixes #565
Description
Adds a new
queryfilterpackage andQueryFilterinterface for implementing declarative logic for filtering query results before the results are passed as input for aQueryCheck. This could be used to apply a check to a certain subset of results or as a lookup mechanism to check a specific result.Filters are implemented at the query check level, so a single test step can have multiple independent query checks with their own filtering.
The current implementations of query filters are:
FilterByDisplayNameExact()FilterByDisplayNameRegexp()FilterByResourceIdentity()This PR also introduces a new
ExpectResourceDisplayNameExact()query check that takes a filter and display name as input and asserts that the display name matches the input after filtering.Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
No